Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@v2/pkg/engine/datasource/grpc_datasource/execution_plan_recursive_test.go`:
- Around line 3-8: The import block currently mixes the local repo import
"github.com/wundergraph/graphql-go-tools/v2/pkg/astparser" with third-party
imports; split imports into separate groups so gci/golangci-lint passes: keep
standard library ("testing") in the first group, third-party
("github.com/stretchr/testify/require") in the second, and the local repo import
("github.com/wundergraph/graphql-go-tools/v2/pkg/astparser") in its own third
group; update the import block in execution_plan_recursive_test.go accordingly.

In `@v2/pkg/engine/datasource/grpc_datasource/execution_plan.go`:
- Around line 689-707: The recursive pointer reuse of RPCMessage via
r.visitedInputTypes prevents planning recursion but breaks
RPCExecutionPlan.String(): formatRPCMessage() traverses field.Message with no
cycle detection and will overflow on recursive inputs; update
RPCExecutionPlan.String() (or formatRPCMessage()) to maintain a visited set
(map[*RPCMessage]struct{} or map[string]struct{}) and check it before recursing
into field.Message, returning a safe placeholder (e.g., "<recursive>") or
short-circuiting when the message pointer/name was already seen; ensure you
reference RPCMessage, field.Message, formatRPCMessage, and visitedInputTypes to
locate the code paths to change.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@v2/pkg/engine/datasource/grpc_datasource/execution_plan_recursive_test.go`:
- Around line 102-104: Two subtests retrieve call := plan.Calls[0] but omit
asserting the RPC method; add assertions for call.MethodName in the 2nd and 3rd
subtests right after call is assigned (same place the first subtest checks
MethodName). Specifically, update the subtests that use plan.Calls and call to
include require.Equal(t, "<expected RPC method string>", call.MethodName) or
require.NotEmpty(t, call.MethodName) as appropriate so regressions in
mapping/planning fail at the root cause; reference the local variables plan,
call and the field MethodName when adding the assertion.

---

Nitpick comments:
In `@v2/pkg/engine/datasource/grpc_datasource/execution_plan_recursive_test.go`:
- Around line 62-63: The assertions use positional indices into
conditionsField.Message.Fields (assigned to andField and orField) which is
fragile; instead locate fields by their JSON/name (e.g., find the Field with
JSONName or Name "and" and the one "or") before validating cycle references.
Update the test helper logic around conditionsField.Message.Fields, andField,
and orField (and the same lookups later in the file where fields are indexed) to
perform an order-independent lookup (search the slice for the matching field
name/JSONPath) and then run the existing cycle-reference assertions against the
found field objects.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@v2/pkg/engine/datasource/grpc_datasource/execution_plan_recursive_test.go`:
- Around line 46-49: Update the stale test comment and strengthen the assertion:
change the comment above the call to plan.String() to note that formatRPCMessage
now tracks visited pointers (so cycle detection exists) instead of saying it has
none, then replace the weak require.NotEmpty(t, result) with a stronger
assertion (e.g., assert the output contains expected markers or has length above
a reasonable threshold) to catch recursion regressions; reference the
plan.String() call and the formatRPCMessage behavior when making the change.

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@v2/pkg/engine/datasource/grpc_datasource/execution_plan_recursive_test.go`:
- Around line 46-49: Update the stale comment to note that formatRPCMessage now
includes cycle detection, and strengthen the assertion by replacing
require.NotEmpty(t, result) with a check that the call to plan.String()
completes and produces a reasonably bounded output (e.g., require.NotEmpty plus
require.Less(t, len(result), 10000) or equivalent) to catch runaway
recursion/format regressions; refer to plan.String() and formatRPCMessage when
making the change.